Debugging with GDB

昨天使用的方案太烦琐，啥都要手工设置，实在折腾不下去了，今天翻墙去android的网站了解了android系统开发的调试手段。建议应用程序开发还是用2.2的NDK调试好了，调完了再改回老一点的版本就行了。下面实验一下系统开发的调试工作。

先给出最简步骤：

cd android系统源码根目录

. build/envsetup.sh

choosecombo

adb forward tcp:5039 tcp:5039

另开一个控制台：

adb shell ps

adb shell gdbserver :5039 --attach pid

正常反馈：

Attached; pid = **** Listening on port 5039

回到原控制台：

gdbclient

成功的话就会加载一系列的符号表。试了一下设置断点，成功地在系统本地码中断了下来。下面要做的就是熟悉GDB调试命令了。

下面附上原文：

The current version of envsetup.sh has a gdbclient command that handles much of the setup. For example, to attach the already-running globaltime application, execute the following, making sure that: 1) you do this from the same window used to build the software on the device you are debugging and 2) verify that the symbols in the object files in the build tree match up with what is installed on the device or emulator.

这两点要求说白了就是只能用于系统开发，当然系统里也可以开发AP，但开发AP也得整个linux环境和android系统实在太折腾。

Android runs gdbserver on the device and an ARM aware gdb, named arm-eabi-gdb, on the desktop machine.

At this point gdb will connect with your device and you should be able to enter c to have the device start executing inside of the desktop gdb session.

If the short instructions don't work, these detailed instructions should:

You should be connected and able to debug as you normally would. You can ignore the error about not finding the location for the thread creation breakpoint. It will be found when the linker loads libc into your process before hitting main(). Also note that the gdb remote protocol doesn't have a way for the device to tell the host about newly created threads so you will not always see notifications about newly created threads. Info about other threads will be queried from the device when a breakpoint is hit or you ask for it by running info thread.